!!!WARNING!!!
nosec detected in the following files: zetaclient/evm/evm_client.go, zetaclient/evm/evm_client_test.go, zetaclient/evm/inbounds.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

Codecov Report

Attention: Patch coverage is 50.23256% with 107 lines in your changes are missing coverage. Please review.

Project coverage is 44.80%. Comparing base (09f99eb) to head (01b4243).

@@             Coverage Diff             @@
##           develop    #1836      +/-   ##
===========================================
+ Coverage    42.97%   44.80%   +1.83%     
===========================================
  Files          217      218       +1     
  Lines        12792    12689     -103     
===========================================
+ Hits          5497     5685     +188     
+ Misses        6852     6553     -299     
- Partials       443      451       +8     

It looks good to me. Wondering if we could consider testing it on local E2E test before moving to production.

It's a good idea. I created a ticket for this as the 1st step: #1856